Repository navigation
fix(acp): settle accepted prompts that fail before turn start - #265
Merged
Merged
Conversation
![kit-code-agent[bot]](https://avatars.githubusercontent.com/in/4797102?s=60&v=4){kind=small}
danielkov
enabled auto-merge (squash)
October 13, 2026 10:59
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Ensure accepted ACP v2 prompts publish a terminal outcome even when publication or execution fails before a logical turn starts. Parent subagent calls can now observe these failures instead of waiting indefinitely for completion.
Technical details
Accepted prompts open an execution-level Running interval before user-message publication or driver execution. Finalization retains cleanup and content-flush ordering before a single Idle terminal, without fabricating a logical TurnStarted or weakening stale-Idle protection.
Failure to publish the initial Running state isolates the session and rejects subsequent prompts before acceptance. Existing queued-input retention after user-message publication failure remains unchanged.